home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
ftp.cs.arizona.edu
/
ftp.cs.arizona.edu.tar
/
ftp.cs.arizona.edu
/
icon
/
newsgrp
/
group95c.txt
/
000040_icon-group-sender _Wed Oct 11 07:45:59 1995.msg
< prev
next >
Wrap
Internet Message Format
|
1996-01-03
|
2KB
Received: by cheltenham.cs.arizona.edu; Wed, 11 Oct 1995 09:41:09 MST
To: icon-group@cs.arizona.edu
Date: 11 Oct 1995 07:45:59 -0400
From: pperucci@access5.digex.net (Phil Perucci)
Message-Id: <45gapn$cv5@access5.digex.net>
Organization: Express Access Online Communications, Greenbelt, MD USA
Sender: icon-group-request@cs.arizona.edu
References: <449s2k$hu8@csnews.cs.colorado.edu>, <MSFRIEDM.95Sep28105413@bingster.us.oracle.com>, <KRISHNA.95Oct9154704@shamu.csd.sgi.com>
Subject: Re: what to use instead of TCL or PERL
Errors-To: icon-group-errors@cs.arizona.edu
In article <KRISHNA.95Oct9154704@shamu.csd.sgi.com>,
Krishna Sethuraman <krishna@shamu.csd.sgi.com> wrote:
>
>Don't forget one very interesting use of Perl -- because of its facility in
>manipulating long strings, it's being used in the human genome mapping project
>(I think that's what it's called). I wouldn't try that in the other scripting
>languages I know of ...
Or... Expect!
While Perl excels at text-processing, Expect (Tcl-based) is intended for
"interaction automation". Expect lets you automate utilities such as
telnet, ftp, passwd - ANYTHING with a character-based interface. Very
handy for those cgi-bin scripts which call other existing applications.
Search the web for "expect" and "nist" (NIST is the home-site) for more
info...
--
==============================================================================
Phil Perucci ......... pperucci@access.digex.net ........ Systems Integrator
"Visit the Hydrologic Information Center at http://www.nohrsc.nws.gov/~hic"
==============================================================================